
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
Server support</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="apptechp131.htm">Previous</A>&nbsp;&nbsp;<A HREF="apptechp133.htm" >Next</A>
<!-- End Header -->
<A NAME="BGBBHDJH"></A><h1>Server support</h1>
<A NAME="TI3991"></A><p>PowerBuilder developers can build clients that invoke the
services of Sybase <ABBR title = "e a server" >EAServer</ABBR>, COM+,
and other application servers, and build components (or objects)
that execute business logic inside each of these servers.</p>
<A NAME="TI3992"></A><p>PowerBuilder also provides support for building clients for
Enterprise JavaBeans components (EJBs) running on any J2EE-compliant
server.</p>
<A NAME="TI3993"></A><h4><ABBR title = "e a server" >EAServer</ABBR></h4>
<A NAME="TI3994"></A><p>PowerBuilder and <ABBR title = "e a server" >EAServer</ABBR> are
fully integrated. A PowerBuilder application can act as a client
to any <ABBR title = "e a server" >EAServer</ABBR> component. In
addition, <ABBR title = "e a server" >EAServer</ABBR> can contain
PowerBuilder custom class user (nonvisual) objects that execute
as middle-tier components.</p>
<A NAME="TI3995"></A><p><ABBR title = "e a server" >EAServer</ABBR> hosts the PowerBuilder
virtual machine natively. This means that <ABBR title = "e a server" >EAServer</ABBR> can
communicate directly with PowerBuilder nonvisual user objects, and
vice versa. <ABBR title = "e a server" >EAServer</ABBR> components
developed in PowerBuilder can take full advantage of the ease of
use and flexibility of PowerScript and the richness of PowerBuilder's
system objects. </p>
<A NAME="TI3996"></A><p>Components developed in PowerBuilder can exploit features
such as transactions, interoperability, and instance pooling. As
shown in <A HREF="apptechp132.htm#BGBDFFAB">Figure 22-1</A>, any
type of client can access any type of component running in <ABBR title = "e a server" >EAServer</ABBR>, regardless of the language
used to develop the component. </p>
<A NAME="BGBDFFAB"></A><caption><b>Figure 22-1: Clients and components in <ABBR title = "e a server" >EAServer</ABBR></b></captionls>
<br><img src="images/distarch.gif">
<A NAME="TI3997"></A><p>For more information, see <A HREF="apptechp133.htm#CBBBFDAD">Chapter 23, "Building an <ABBR title = "e a server" >EAServer</ABBR> Component"</A> and <A HREF="apptechp147.htm#CDECHFMK">Chapter 24, "Building an <ABBR title = "e a server" >EAServer</ABBR> Client ."</A></p>
<A NAME="TI3998"></A><h4>J2EE servers</h4>
<A NAME="TI3999"></A><p>J2EE, the Java 2 Platform, Enterprise Edition, is the official
Java framework for enterprise application development. A J2EE application
is composed of separate components that are installed on different
computers in a multitiered system. <A HREF="apptechp132.htm#BGBIEJHE">Figure 22-2</A> shows three tiers in this system:
the client tier, middle tier, and Enterprise Information Systems
(EIS) tier. The middle tier is sometimes considered to be made up
of two separate tiers: the Web tier and the business tier.</p>
<A NAME="BGBIEJHE"></A><caption><b>Figure 22-2: J2EE client, middle, and
EIS tiers</b></captionls>
<br><img src="images/j2ee1.gif">
<A NAME="TI4000"></A><p>Client components, such as application clients and applets,
run on computers in the client tier. Web components, such as Java
servlets and JavaServer Pages (JSP) components, run on J2EE servers
in the Web tier. Enterprise JavaBeans (EJB) components are business
components and run on J2EE servers in the business tier. The EIS
tier is made up of servers running relational database management
systems, enterprise resource planning applications, mainframe transaction
processing, and other legacy information systems.</p>
<A NAME="TI4001"></A><p>In PowerBuilder, you can build client applications that use
the services of EJB components running on any J2EE-compliant server.
For more information, see <A HREF="apptechp180.htm#CDECHFKM">Chapter 28, "Building an EJB client ."</A></p>
<A NAME="BABCJBEH"></A><h4>Plug-in for J2EE servers</h4>
<A NAME="TI4002"></A><p>You can also deploy custom class user objects to third-party
application servers on which the PowerBuilder Application Server
Plug-in is installed. The plug-in is a Sybase product that
supports several application servers. Wizards that help you generate
application server components that you can deploy to these servers
and proxies that you can use to build client applications are built
into PowerBuilder, but you must install the plug-in product separately.
The wizards and techniques are very similar to those used for building <ABBR title = "e a server" >EAServer</ABBR> components and clients.
For more information, see the documentation for the PowerBuilder
Application Server Plug-in on the <A HREF="http://www.sybase.com/support/manuals/">Product Manuals Web site</A>
.</p>
<A NAME="TI4003"></A><h4>COM+</h4>
<A NAME="TI4004"></A><p>A PowerBuilder application can act as a client to a COM server.
The server can be built using PowerBuilder or any other COM-compliant
application development tool and it can run locally, on a remote
computer as an in-process server, or in COM+, as shown
in <A HREF="apptechp132.htm#BGBIAIAH">Figure 22-3</A>.</p>
<A NAME="BGBIAIAH"></A><caption><b>Figure 22-3: PowerBuilder clients for
COM components</b></captionls>
<br><img src="images/dpbimts.gif">
<p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Deprecated technology</span> <A NAME="TI4005"></A>COM and COM+ are deprecated technologies and might
not be supported in future releases of PowerBuilder.</p>
<A NAME="TI4006"></A><p>You can develop a custom class user object containing business
logic in PowerBuilder and then package the object as a COM object.
A PowerBuilder COM server can include one or more PowerBuilder custom
class user objects. You code the user objects in the User Object
painter and then build the server in the Project painter. You can
also deploy the COM server directly to a local COM+ server
or create a COM+ package from the Project painter.</p>
<A NAME="TI4007"></A><p>For more information, see <A HREF="apptechp175.htm#CHDBJEFH">Chapter 27, "Building a COM or COM+ Client."</A></p>

